home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000173_news@columbia.edu_Thu Aug 17 03:56:15 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA10110
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 17 Aug 1995 02:02:13 -0400
Received: by apakabar.cc.columbia.edu id AA23415
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 17 Aug 1995 02:02:11 -0400
Path: news.columbia.edu!panix!bloom-beacon.mit.edu!news5.ner.bbnplanet.net!news3.near.net!sun3.ipswitch.com!ddl
From: ddl@harvard.edu (Dan Lanciani)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit initialization on TCP/IP
Message-Id: <2961@sun3.IPSWITCH.COM>
Date: 17 Aug 95 03:56:15 GMT
References: <1995Aug8.075939.58350@cc.usu.edu> <40f1kp$mor@harbour.awod.com>
Organization: Internet
Lines: 30
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <40f1kp$mor@harbour.awod.com>, Carl Hilton writes:
[... attribution level lost ...]
| >
| > > On machine 2. I am running WFW3.11 with MS's TCPIP stack for WFW. I've
| > >tried shelling out to DOS and running WINPKT and even running WINPKT before
| > >I launch WFW but I keep getting the same error.
| >
| > MS' TCP/IP stack isn't for DOS programs.
| >
|
| So there is NO way to run kermit from this configuration?
Some people have been able to run kermit & MSTCP32 w/WfWG 3.11 together
using my ndis3pkt.386 driver. The trick is to use different IP addresses
for MSTCP32 and kermit. More generally, you need one IP address for
MSTCP32 and one IP address for all your other packet-driver applications.
This is because, although ndis3pkt includes a tcp session multiplexor
that allows multiple packet-driver-based tcp/ip stacks to share the same
IP address on one machine, ndis3pkt has no control over the MSTCP32
stack. If you try to use the same address for both, MSTCP32 will reset
kermit's connections and such.
Some people have been unable to get the MSTCP32+kermit+ndis3pkt combination
to work in configurations that appear superficially identical to those
which work elsewhere. I suspect there is some minor detail of interest
to be found here, but I don't know what it is. :)
Dan Lanciani
ddl@harvard.*